AOP for Everyone - Cracking the Multiple Weavers Problem

ion Layers for Aspect Languages A difficulty in using term rewriting systems is the inherent nature of the transforms, which requires knowledge about parsing and the underlying grammar to write complex rewrite functions. This raises unintentional accidental complexities and impedes the adoption of such systems in mainstream software development. Because of these idiosyncrasies, developers may prefer to deal with object-based or XML-based transforms, which are conceptually easier to work with, but do not offer the desired level of scalability. Our current work offers a technique to build simple convenience layers (i.e., aspect languages layered above a transformation engine) to mitigate these accidental complexities to enable AOP based on term rewriting. For example, the rewrite rule shown in Listing 1b can be declaratively specified by an aspect (as shown below) and then translated to its low-level form as required by the term rewriting system. In this example, the special compose functor is used to wrap the try-finally statement before and after the execution of the Handle method. aspect synchronizeDBErrHandler{ pointcut function_handle() : execution(function *.Handle(..)); before():function_handle() { TExHandler (Collection).LockHandle; } after():function_handle() { TExHandler (Collection).UnLockHandle; } compose():try-finally (thisJoinPoint);